home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
rcsmerge.z
/
rcsmerge
Wrap
Text File
|
1998-10-20
|
7KB
|
199 lines
RRRRCCCCSSSSMMMMEEEERRRRGGGGEEEE((((1111)))) RRRRCCCCSSSSMMMMEEEERRRRGGGGEEEE((((1111))))
NNNNAAAAMMMMEEEE
rcsmerge - merge RCS revisions
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
rrrrccccssssmmmmeeeerrrrggggeeee [_o_p_t_i_o_n_s] _f_i_l_e
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
rrrrccccssssmmmmeeeerrrrggggeeee incorporates the changes between two revisions of an RCS file
into the corresponding working file.
Pathnames matching an RCS suffix denote RCS files; all others denote
working files. Names are paired as explained in cccciiii(1).
At least one revision must be specified with one of the options described
below, usually ----rrrr. At most two revisions may be specified. If only one
revision is specified, the latest revision on the default branch
(normally the highest branch on the trunk) is assumed for the second
revision. Revisions may be specified numerically or symbolically.
rrrrccccssssmmmmeeeerrrrggggeeee prints a warning if there are overlaps, and delimits the
overlapping regions as explained in mmmmeeeerrrrggggeeee(1). The command is useful for
incorporating changes into a checked-out revision.
OOOOPPPPTTTTIIIIOOOONNNNSSSS
----AAAA Output conflicts using the ----AAAA style of ddddiiiiffffffff3333(1), if supported by
ddddiiiiffffffff3333. This merges all changes leading from _f_i_l_e_2 to _f_i_l_e_3 into
_f_i_l_e_1, and generates the most verbose output.
----EEEE, ----eeee
These options specify conflict styles that generate less information
than ----AAAA. See ddddiiiiffffffff3333(1) for details. The default is ----EEEE. With ----eeee,
rrrrccccssssmmmmeeeerrrrggggeeee does not warn about conflicts.
----kkkk_s_u_b_s_t
Use _s_u_b_s_t style keyword substitution. See ccccoooo(1) for details. For
example, ----kkkkkkkk ----rrrr1111....1111 ----rrrr1111....2222 ignores differences in keyword values when
merging the changes from 1111....1111 to 1111....2222. It normally does not make
sense to merge binary files as if they were text, so rrrrccccssssmmmmeeeerrrrggggeeee
refuses to merge files if ----kkkkbbbb expansion is used.
----pppp[_r_e_v]
Send the result to standard output instead of overwriting the
working file.
----qqqq[_r_e_v]
Run quietly; do not print diagnostics.
----rrrr[_r_e_v]
Merge with respect to revision _r_e_v. Here an empty _r_e_v stands for
the latest revision on the default branch, normally the head.
PPPPaaaaggggeeee 1111
RRRRCCCCSSSSMMMMEEEERRRRGGGGEEEE((((1111)))) RRRRCCCCSSSSMMMMEEEERRRRGGGGEEEE((((1111))))
----TTTT This option has no effect; it is present for compatibility with
other RCS commands.
----VVVV Print RCS's version number.
----VVVV_n Emulate RCS version _n. See ccccoooo(1) for details.
----xxxx_s_u_f_f_i_x_e_s
Use _s_u_f_f_i_x_e_s to characterize RCS files. See cccciiii(1) for details.
----zzzz_z_o_n_e
Use _z_o_n_e as the time zone for keyword substitution. See ccccoooo(1) for
details.
EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
Suppose you have released revision 2.8 of ffff....cccc. Assume furthermore that
after you complete an unreleased revision 3.4, you receive updates to
release 2.8 from someone else. To combine the updates to 2.8 and your
changes between 2.8 and 3.4, put the updates to 2.8 into file f.c and
execute
rrrrccccssssmmmmeeeerrrrggggeeee ----pppp ----rrrr2222....8888 ----rrrr3333....4444 ffff....cccc >>>>ffff....mmmmeeeerrrrggggeeeedddd....cccc
Then examine ffff....mmmmeeeerrrrggggeeeedddd....cccc. Alternatively, if you want to save the updates
to 2.8 in the RCS file, check them in as revision 2.8.1.1 and execute ccccoooo
----jjjj:
cccciiii ----rrrr2222....8888....1111....1111 ffff....cccc
ccccoooo ----rrrr3333....4444 ----jjjj2222....8888::::2222....8888....1111....1111 ffff....cccc
As another example, the following command undoes the changes between
revision 2.4 and 2.8 in your currently checked out revision in ffff....cccc.
rrrrccccssssmmmmeeeerrrrggggeeee ----rrrr2222....8888 ----rrrr2222....4444 ffff....cccc
Note the order of the arguments, and that ffff....cccc will be overwritten.
EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
RRRRCCCCSSSSIIIINNNNIIIITTTT
options prepended to the argument list, separated by spaces. See
cccciiii(1) for details.
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
Exit status is 0 for no overlaps, 1 for some overlaps, 2 for trouble.
IIIIDDDDEEEENNNNTTTTIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN
Author: Walter F. Tichy.
Revision Number: 5.7; Release Date: 1998/01/12.
Copyright c 1982, 1988, 1989 by Walter F. Tichy.
Copyright c 1990, 1991, 1992, 1993, 1994, 1995 by Paul Eggert.
PPPPaaaaggggeeee 2222
RRRRCCCCSSSSMMMMEEEERRRRGGGGEEEE((((1111)))) RRRRCCCCSSSSMMMMEEEERRRRGGGGEEEE((((1111))))
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ci(1), co(1), ident(1), merge(1), rcs(1), rcsdiff(1), rcsintro(1),
rlog(1), rcsfile(4), RCSsource(5)
Walter F. Tichy, RCS--A System for Version Control, _S_o_f_t_w_a_r_e--_P_r_a_c_t_i_c_e &
_E_x_p_e_r_i_e_n_c_e 11115555, 7 (July 1985), 637-654.
PPPPaaaaggggeeee 3333